NTISthis.com

Evidence Guide: ICTSAD606 - Analyse stakeholder requirements

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAD606 - Analyse stakeholder requirements

What evidence can you provide to prove your understanding of each of the following citeria?

Prioritise requirements

  1. Determine the basis for prioritisation of requirements
  2. Resolve challenges in facilitating the prioritisation
Determine the basis for prioritisation of requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Resolve challenges in facilitating the prioritisation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Organise requirements

  1. Articulate requirements at an appropriate level of abstraction
  2. Devise appropriate models to describe the solution scope, based on informational needs of stakeholders
  3. Document dependencies and inter-relationships among requirements
Articulate requirements at an appropriate level of abstraction

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Devise appropriate models to describe the solution scope, based on informational needs of stakeholders

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document dependencies and inter-relationships among requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Specify and model requirements

  1. Develop textual requirements
  2. Generate matrices to convey or support identified requirements
  3. Create models to document and communicate requirements and improvement opportunities
Develop textual requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Generate matrices to convey or support identified requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create models to document and communicate requirements and improvement opportunities

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define assumptions and constraints

  1. Agree on assumptions to be defined and clarified as requirements are understood
  2. Document and examine business constraints to identify options no longer available
  3. Recognise and examine technical constraints that may restrict design or mandate standards to be followed
Agree on assumptions to be defined and clarified as requirements are understood

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document and examine business constraints to identify options no longer available

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Recognise and examine technical constraints that may restrict design or mandate standards to be followed

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Verify requirements

  1. Establish characteristics of requirements’ quality
  2. Undertake verification activities iteratively throughout the requirements analysis process
Establish characteristics of requirements’ quality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Undertake verification activities iteratively throughout the requirements analysis process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate requirements

  1. Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed
  2. Generate measurable evaluation criteria to assess success of requirements benefit post implementation
  3. Assign business value of requirements to assist in identifying candidates for elimination
  4. Determine requirement dependencies for benefits realisation
  5. Evaluate alignment with business case and opportunity cost to assist validation and decision making
Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Generate measurable evaluation criteria to assess success of requirements benefit post implementation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assign business value of requirements to assist in identifying candidates for elimination

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine requirement dependencies for benefits realisation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate alignment with business case and opportunity cost to assist validation and decision making

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prioritise requirements

1.1 Determine the basis for prioritisation of requirements

1.2 Resolve challenges in facilitating the prioritisation

2. Organise requirements

2.1 Articulate requirements at an appropriate level of abstraction

2.2 Devise appropriate models to describe the solution scope, based on informational needs of stakeholders

2.3 Document dependencies and inter-relationships among requirements

3. Specify and model requirements

3.1 Develop textual requirements

3.2 Generate matrices to convey or support identified requirements

3.3 Create models to document and communicate requirements and improvement opportunities

4. Define assumptions and constraints

4.1 Agree on assumptions to be defined and clarified as requirements are understood

4.2 Document and examine business constraints to identify options no longer available

4.3 Recognise and examine technical constraints that may restrict design or mandate standards to be followed

5. Verify requirements

5.1 Establish characteristics of requirements’ quality

5.2 Undertake verification activities iteratively throughout the requirements analysis process

6. Validate requirements

6.1 Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed

6.2 Generate measurable evaluation criteria to assess success of requirements benefit post implementation

6.3 Assign business value of requirements to assist in identifying candidates for elimination

6.4 Determine requirement dependencies for benefits realisation

6.5 Evaluate alignment with business case and opportunity cost to assist validation and decision making

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prioritise requirements

1.1 Determine the basis for prioritisation of requirements

1.2 Resolve challenges in facilitating the prioritisation

2. Organise requirements

2.1 Articulate requirements at an appropriate level of abstraction

2.2 Devise appropriate models to describe the solution scope, based on informational needs of stakeholders

2.3 Document dependencies and inter-relationships among requirements

3. Specify and model requirements

3.1 Develop textual requirements

3.2 Generate matrices to convey or support identified requirements

3.3 Create models to document and communicate requirements and improvement opportunities

4. Define assumptions and constraints

4.1 Agree on assumptions to be defined and clarified as requirements are understood

4.2 Document and examine business constraints to identify options no longer available

4.3 Recognise and examine technical constraints that may restrict design or mandate standards to be followed

5. Verify requirements

5.1 Establish characteristics of requirements’ quality

5.2 Undertake verification activities iteratively throughout the requirements analysis process

6. Validate requirements

6.1 Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed

6.2 Generate measurable evaluation criteria to assess success of requirements benefit post implementation

6.3 Assign business value of requirements to assist in identifying candidates for elimination

6.4 Determine requirement dependencies for benefits realisation

6.5 Evaluate alignment with business case and opportunity cost to assist validation and decision making

Evidence of the ability to:

define, specify and prioritise stakeholder and solution requirements to a standard that would allow construction of a business solution

verify and validate the requirements to ensure necessary quality, and support for stakeholder needs.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

describe business rules analysis

explain data flow diagramming

outline data, organisation and process modelling, and their relevant business and technical constraints

explain functional decomposition

describe risk management strategies

explain the purpose of using scenarios, stories and case studies

describe scope modelling.